Skip to content

Component brain instructions - #1

Merged
robfromboulder merged 32 commits into
mainfrom
component-brains
Aug 8, 2026
Merged

Component brain instructions#1
robfromboulder merged 32 commits into
mainfrom
component-brains

Conversation

@robfromboulder

@robfromboulder robfromboulder commented Aug 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds MBT_COMPONENTS.md and templates/COMPONENTS_CLAUDE.md — an opt-in convention for brains whose knowledge divides into several components, each with its own namespace, directory, and work-item log
  • Hardens the full seeding path (create-brain, check-brain, session closeout, work setup/closeout, and work scaffolds) against component-brain edge cases: two-tier placeholder contract, longest-prefix naming constraint, log routing rules, and restructuring procedures
  • Refocuses SCOPE authoring guidance on the problem space — the scope/approach templates, MBT_CREATE_BRAIN.md's authoring rules, and MBT_CHECK_BRAIN.md's drift check (MBT_SCOPE.md itself is unchanged)
  • Updates MBT_PATTERN.md, MBT_DREAM_CYCLE.md, CLAUDE.md, and all affected templates
  • Closes twenty-one findings from the pre-merge review, one fix per commit so the branch reads as atomic diffs

Test plan

  • Bootstrap a new single-component brain using MBT_CREATE_BRAIN.md and verify no regressions
  • Bootstrap a new multi-component brain and verify placeholder substitution, log routing, and work-item scaffolding
  • Run MBT_CHECK_BRAIN.md against both brain types

Run on 2026-08-08 against fixture brains seeded from the templates literally — a single-unit brain and a three-level component brain covering nested tokens, a non-nested token, and a sub-component. Both seeds executed with no improvisation: two-tier placeholder contract, per-unit substitution, registry fill, and README reword all behaved as written, and the check procedure passed on both. A deliberately misplaced document (a child-token file at the hub root) was caught by the new anchored namespace check. The one defect the run surfaced was pre-existing and is fixed here (a87c3fd). Every runnable check command was also executed against fixtures including its failure cases, which is what caught the three that failed open under zsh.

Follow-ups

Three work items land as dormant scaffolds in working/, each gated on a living multi-component brain rather than designed on paper. They ship separately when their triggers fire:

  • MIGRATIONS — an extraction kit for a component leaving as its own brain
  • REHOMING — a move procedure for a work item that outgrows its owning unit
  • COMPONENT_DREAM — a component-aware dream cycle, and the cycle as the component registry's assigned maintainer. Until it lands, MBT_CREATE_BRAIN.md warns against instantiating the dream-cycle template unadapted into a component brain

robfromboulder and others added 4 commits July 31, 2026 09:52
Introduces MBT_COMPONENTS.md (V1) and templates/COMPONENTS_CLAUDE.md to support
brains whose knowledge divides into several components, each with its own
namespace, directory, and work-item log. Updates MBT_PATTERN.md, MBT_CREATE_BRAIN.md,
MBT_CHECK_BRAIN.md, CLAUDE.md, and all affected templates to reflect the layer;
fixes namespace-token gaps and the session-closeout fallback for multi-log brains.
An adversarial pass over MBT_COMPONENTS, MBT_CREATE_BRAIN, and every template a component brain instantiates, using the virtual-view-brain bootstrap plan as the reference case and both exemplar brains as compatibility checks. Establishes the two-tier placeholder contract — <PREFIX> is the brain/hub token resolved at creation, <TOKEN> the owning unit's token resolved at runtime — across the session-closeout, work-setup/closeout, and work scaffolds, whose patterns previously corrupted under substitution in component brains. Pins the routing ambiguities: sessions log to the nearest common ancestor of the units their work concerned (not merely read), a work item's merged log entries all land in its owner's canonical log, and questions no component claims are hub-level. Adds the longest-prefix naming constraint (a parent's name must not extend into a child's token) with guardrails where names get chosen, corrects the restructuring rows (a fresh hub token with maintenance-doc renames; migrated platform units author their missing SCOPE/APPROACH; children are seeded and parents cede content), restores dropped rules to the component entrypoint template (never a bare CLAUDE.md, logs never archived, move-not-delete retirement, maturity blocks), sanctions log-appending procedures citing the session-closeout format authority, renames the work-item "prefix" to slug, and makes instantiated brains self-contained by inlining the six work scaffolds. The toolkit's own dream cycle now sweeps the spec-template pair for drift. The point-in-time review is archived as MBT_COMPOUND_FABLE_REVIEW; the remaining open items — the component dream cycle, work-item re-homing, registry maintenance, and the two migration holes — stand as working/MBT_COMPOUND_RESEARCH with per-area confidence scores.
@robfromboulder robfromboulder self-assigned this Aug 5, 2026
@robfromboulder
robfromboulder merged commit f841a05 into main Aug 8, 2026
@robfromboulder
robfromboulder deleted the component-brains branch August 8, 2026 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant